What (who) is requirements capture - definition

PROCESS OF DEFINING, DOCUMENTING, AND MAINTAINING REQUIREMENTS IN THE ENGINEERING DESIGN PROCESS

Requirements Engineering; Requirement engineering; Requirements engineer

Electron capture

PROCESS IN WHICH A PROTON-RICH NUCLIDE ABSORBS AN INNER ATOMIC ELECTRON

Epsilon decay; K-Capture; K-capture; EC decay; Electron capture decay; L-electron capture; K-electron capture; K capture; L capture; L-capture; Inverse-beta decay; Electron-capture; Electron Capture; K Capture; K Captures; Electron Captures; K-Electron Capture; K Electron Capture; K Electron Captures; K-Electron Captures

Electron capture (K-electron capture, also K-capture, or L-electron capture, L-capture) is a process in which the proton-rich nucleus of an electrically neutral atom absorbs an inner atomic electron, usually from the K or L electron shells. This process thereby changes a nuclear proton to a neutron and simultaneously causes the emission of an electron neutrino.

https://en.wikipedia.org/wiki/Electron_capture

Software requirements specification

A SET OF FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS THAT A PIECE OF DESIGNED SOFTWARE NEEDS TO FULFIL, MAY INCLUDE A SET OF USE CASES

Requirements specification; IEEE 830; Req spec; Requirements specifications; Software Requirements Specification

A SOFTWARE REQUIREMENTS SPECIFICATION (SRS) is a description of a software system to be developed. It is modeled after business requirements specification (CONOPS).

https://en.wikipedia.org/wiki/Software_requirements_specification

Requirements elicitation

PRACTICE OF COLLECTING THE REQUIREMENTS OF A SYSTEM FROM USERS, CUSTOMERS AND OTHER STAKEHOLDERS

Requirements gathering; Requirement gathering; Requirements inception

In requirements engineering, requirements elicitation is the practice of researching and discovering the requirements of a system from users, customers, and other stakeholders.Requirements Engineering A good practice guide, Ramos Rowel and Kurts Alfeche, John Wiley and Sons, 1997 The practice is also sometimes referred to as "requirement gathering".

https://en.wikipedia.org/wiki/Requirements_elicitation

Wikipedia

Requirements engineering

Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering.

The first use of the term requirements engineering was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference.

In the waterfall model, requirements engineering is presented as the first phase of the development process. Later development methods, including the Rational Unified Process (RUP) for software, assume that requirements engineering continues through a system's lifetime.

Requirements management, which is a sub-function of Systems Engineering practices, is also indexed in the International Council on Systems Engineering (INCOSE) manuals.

https://en.wikipedia.org/wiki/Requirements engineering